feat: Create centralized way to style with tailwindcss - #43
Conversation
|
@Josem1801 See this just to know how this project will evolve. |
|
I need feedback to select the class prefix for components:
|
@Brayan-724 I personally like |
|
Maybe it's a little obvious but could we use a name? I mean, this is a library right? 😃 Jajxjad |
Yes, but is an internal one. The library doesn't pretend to be downloaded by external developers, just for those who want our specific design.
If you have a name to suggest, I'm open to listen you, but is not a key-point to be searchable because the README.md shows how to install it. |
|
@Brayan-724 Personally, I prefer the first one:
However, if it might create conflicts in the future, |
|
@Brayan-724 owo
Oh! Okay I understand what do you mean, but anyone could just download the library and use it, I mean it's not exactly internal if you have the code public, and you don't use a private registry, anyone could download the library and use it, but yeah Understanding that it's Tailwind I prefer something like: <div class="rles-component" />Why? Because if you choose the last one you need to write a lot just to start to define the style and usually for tailwind you use at least 5 classes, so could extend a lot the length of a line. Not for any other reason, to be honest, it's the same.
I change my opinion now ✨ |
364af00 to
aecaa7c
Compare
For expand the support of UI frameworks/libraries and don't copy-paste styles of each component, I create a centralized tailwindcss definitions that will be shared between all technologies.